Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 93.52%. Comparing base (d8e10c7) to head (dcbef10).
Report is 42 commits behind head on main.

@@            Coverage Diff             @@
##             main     #101      +/-   ##
==========================================
+ Coverage   90.55%   93.52%   +2.96%     
==========================================
  Files           8       12       +4     
  Lines         180      463     +283     
==========================================
+ Hits          163      433     +270     
- Misses         17       30      +13     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests

None of the evaluations are working because I get a GRPC.unavailable error when I try to resolve them. This might be related to the open issues. @toddbaert @beeme1mr fyi

@aepfli what issue are you referring to?

@aepfli what issue are you referring to?

nvm I found the issue, the docker container took longer than expected to be available - now there are only 4 test cases missing, and we run the basic test suite as we do for js for the rpc provider - reconnect is something which i will do at a later stage

Could you please add a section in the contributing doc that explains how to run the e2e tests?

So far, the command has not changed for execution. It runs with hatch run test, like before - if we want to split this, I would extract this into something separate. My Python tooling knowledge is not in a state, where I can easily do this

Ready to be reviewed @toddbaert @beeme1mr @open-feature/sdk-python-approvers @open-feature/sdk-python-maintainers

flagD -> flagd but otherwise approved, and very grateful! 🙏

renamed - but we always pronounce it "flag D" else it looks more like "flagged" - just my few cents

flagD -> flagd but otherwise approved, and very grateful! 🙏

renamed - but we always pronounce it "flag D" else it looks more like "flagged" - just my few cents

https://flagd.dev/reference/naming/